Fractal flames are a member of the iterated function system class[1] of fractals created by Scott Draves in 1992.[2] Draves' open-source code was later ported into Adobe After Effects graphics software[3] and translated into the Apophysis fractal flame editor.[2]
Fractal flames differ from ordinary iterated function systems in three ways:
The tone mapping and coloring are designed to display as much of the detail of the fractal as possible, which generally results in a more aesthetically pleasing image.
Contents |
The algorithm consists of two steps: creating a histogram and then rendering the histogram.
First one iterates a set of functions, starting from a randomly chosen point P = (P.x,P.y,P.c), where the third coordinate indicated the current color of the point.
In each iteration, choose one of the functions above where the probability that Fj is chosen is pj. Then one computes the next iteration of P by applying Fj on (P.x,P.y).
Each individual function has the following form:
where the parameter wk is called the weight of the variation Vk. Draves suggests [4] that all :s are non-negative and sum to one, but implementations such as Apophysis do not impose that restriction.
The functions Vk are a set of predefined non-linear functions. A few examples[4] are
The colour P.c of the point is blended with the color associated with the latest applied function Fj:
After each iteration, one updates the histogram at the point corresponding to (P.x,P.y). This is done as follows:
histogram[x][y][FREQUENCY] := histogram[x][y][FREQUENCY]+1 histogram[x][y][COLOR] := (histogram[x][y][COLOR] + P.c )/2
The colours in the image will therefore reflect what functions that was used to get to that part of the image.
To increase the quality of the image, one can use supersampling to decrease the noise. This involves creating a histogram larger than the image so each pixel has multiple data points to pull from.
For example, creating a histogram with 300×300 cells in order to draw an 100×100 px image. Each pixel would use a 3×3 group of histogram buckets to calculate its value.
For each pixel (x,y) in the final image, do the following computations:
frequency_avg[x][y] := average_of_histogram_cells_frequency(x,y); color_avg[x][y] := average_of_histogram_cells_color(x,y); alpha[x][y] := log(frequency_avg[x][y]) / log(frequency_max); //frequency_max is the maximal number of iterations that hit a cell in the histogram. final_pixel_color[x][y] := color_avg[x][y] * alpha[x][y]^(1/gamma); //gamma is a value greater than 1.
The algorithm above uses gamma correction to make the colors appear brighter. This is implemented in for example the Apophysis software.
To increase the quality even more, one can use gamma correction on each individual color channel, but this is a very heavy computation, since the log function is slow.
A simplified algorithm would be to let the brightness be linearly dependent on the frequency:
final_pixel_color[x][y] := color_avg[x][y] * frequency_avg[x][y]/frequency_max;
but this would make some parts of the fractal lose detail, which is undesirable.[4]
The flame algorithm is like a Monte Carlo simulation, with the flame quality directly proportional to the number of iterations of the simulation. The noise that results from this stochastic sampling can be reduced by blurring the image, to get a smoother result in less time. One does not however want to lose resolution in the parts of the image that receive many samples and so have little noise.
This problem can be solved with adaptive density estimation to increase image quality while keeping render times to a minimum. FLAM3 uses a simplification of the methods presented in *Adaptive Filtering for Progressive Monte Carlo Image Rendering*, a paper presented at WSCG 2000 by Frank Suykens and Yves D. Willems. The idea is to vary with width of the filter inversely proportional to the number of samples available.
As a result, areas with few samples and lots of noise get blurred and smoothed, but areas with lots of samples and low noise are left unaffected. See http://code.google.com/p/flam3/wiki/DensityEstimation.
Not all Flame implementations use Density Estimation.